fix(etl): enforce accepted status URL invariant - #273
Conversation
|
Warning Review limit reached
Next review available in: 22 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Fixes #272.
Strict fail-first branch from exact protected
develop@942d164ceb7af497bb28a95f842db96429d1bdc4.Current test-only head
8caddd09147286792216fcce953e30cda690153eadds a dedicated production-boundary test class rather than touchingEtlJobModelTest, which is owned by the active #271 writer. Protected source accepts blank, absolute, authority-bearing, and non-root-relativestatusUrlvalues despite documenting an origin-relative monitor resource contract. Hosted RED must therefore be a focused assertion failure fromEtlJobAcceptedResponseStatusUrlTestafter normal compile/startup; dependency/setup/fixture failure is not valid RED.After valid RED, the narrow GREEN may touch only
EtlJobAcceptedResponseplus this focused test unless fresh evidence requires less. Preserve the valid/api/etl/jobs/{uuid}response, UUID/status semantics, controller location construction, durable-job persistence, active #271 lifecycle work, #121 stack, and canonical docs #149. Checks/reviews on the RED head or any predecessor do not transfer to a later implementation head.